Complete Linux

home *** CD-ROM | disk | FTP | other *** search

/ Complete Linux / Complete Linux.iso / docs / apps / database / ingres04.lzh / doc / error / 05dbu.doc < prev

Wrap

Text File | 1992-11-19 | 13.6 KB | 381 lines

DBU(ERROR) 3/30/79 DBU(ERROR) NAME Data Base Utility error message summary SYNOPSIS Error numbers 5000 - 5999 DESCRIPTION The Data Base Utility functions perform almost all tasks which are not directly associated with processing queries. The error messages which they can generate result from some syntax checking and a considerable amount of semantic check- ing. ERRORS 5001 PRINT: bad relation name %0 You are trying to print a relation which doesn't ex- ist. 5002 PRINT: %0 is a view and can't be printed The only way to print a view is by retrieving it. 5003 PRINT: Relation %0 is protected. You are not authorized to access this relation. 5102 CREATE: duplicate relation name %0 You are trying to create a relation which already exists. 5103 CREATE: %0 is a system relation You cannot create a relation with the same name as a system relation. The system depends on the fact that the system relations are unique. 5104 CREATE %0: invalid attribute name %1 This will happen if you try to create a relation with an attribute longer than 12 characters. 5105 CREATE %0: duplicate attribute name %1 Attribute names in a relation must be unique. You are trying to create one with a duplicated name. 5106 CREATE %0: invalid attribute format "%2" on attri- bute %1 The allowed formats for a domain are c1-c255, i1, i2, i4, f4 and f8. Any other format will generate this error. 5107 CREATE %0: excessive domain count on attribute %1 A relation cannot have more than 49 domains. The origin of this magic number is obscure. This is very difficult to change. 5108 CREATE %0: excessive relation width on attribute %1 The maximum number of bytes allowed in a tuple is 1010. This results from the decision that a tuple must fit on one UNIX "page". Assorted pointers re- quire the 14 bytes which separates 1010 from 1024. This "magic number" is very hard to change. 5201 DESTROY: %0 is a system relation The system would immediately stop working if you were allowed to do this. 5202 DESTROY: %0 does not exist or is not owned by you To destroy a relation, it must exist, and you must own it. 5203 DESTROY: %0 is an invalid integrity constraint iden- tifier Integers given do not identify integrity constraints on the specified relation. For example: If you were to type "destroy permit parts 1, 2, 3", and 1, 2, or 3 were not the numbers "help permit parts" prints out for permissions on parts, you would get this er- ror. 5204 DESTROY: %0 is an invalid protection constraint identifier Integers given do not identify protection con- straints on the specified relation. Example as for error 5203. 5300 INDEX: cannot find primary relation The relation does not exist - check your spelling. 5301 INDEX: more than maximum number of domains A secondary index can be created on at most six domains. 5302 INDEX: invalid domain %0 You have tried to create an index on a domain which does not exist. 5303 INDEX: relation %0 not owned by you You must own relations to put indicies on them. 5304 INDEX: relation %0 is already an index INGRES does not permit tertiary indicies. 5305 INDEX: relation %0 is a system relation Secondary indices cannot be created on system rela- tions. 5306 INDEX: %0 is a view and an index can't be built on it Since views are not physically stored in the data- base, you cannot build indicies on them. 5401 HELP: relation %0 does not exist 5402 HELP: cannot find manual section "%0" Either the desired manual section does not exist, or your system does not have any on-line documentation. 5403 HELP: relation %0 is not a view Did a "help view" (which prints view definition) on a nonview. For example: "help view overpaidv" prints out overpaidv's view definition. 5404 HELP: relation %0 has no permissions on it granted 5405 HELP: relation %0 has no integrity constraints on it You have tried to print the permissions or integrity constraints on a relation which has none specified. 5410 HELP: tree buffer overflowed 5411 HELP: tree stack overflowed Still more buffer overflows. 5500 MODIFY: relation %0 does not exist 5501 MODIFY: you do not own relation %0 You cannot modify the storage structure of a rela- tion you do not own. 5502 MODIFY %0: you may not provide keys on a heap By definition, heaps do not have keys. 5503 MODIFY %0: too many keys provided You can only have 49 keys on any relation. 5504 MODIFY %0: cannot modify system relation System relations can only be modified by using the _s_y_s_m_o_d command to the shell; for example sysmod _d_b_n_a_m_e 5507 MODIFY %0: duplicate key "%1" You may only specify a domain as a key once. 5508 MODIFY %0: key width (%1) too large for isam When modifying a relation to isam, the sum of the width of the key fields cannot exceed 245 bytes. 5510 MODIFY %0: bad storage structure "%1" The valid storage structure names are heap, cheap, isam, cisam, hash, and chash. 5511 MODIFY %0: bad attribute name "%1" You have specified an attribute that does not exist in the relation. 5512 MODIFY %0: "%1" not allowed or specified more than once You have specified a parameter which conflicts with another parameter, is inconsistant with the storage mode, or which has already been specified. 5513 MODIFY %0: fillfactor value %1 out of bounds _F_i_l_l_f_a_c_t_o_r must be between 1 and 100 percent. 5514 MODIFY %0: minpages value %1 out of bounds _M_i_n_p_a_g_e_s must be greater than zero. 5515 MODIFY %0: "%1" should be "fillfactor", "maxpages", or "minpages" You have specified an unknown parameter to _m_o_d_i_f_y. 5516 MODIFY %0: maxpages value %1 out of bounds 5517 MODIFY %0: minpages value exceeds maxpages value 5518 MODIFY %0: invalid sequence specifier "%1" for domain %2. Sequence specifier may be ``ascending'' (or ``a'') or ``descending'' (or ``d'') in a _m_o_d_i_f_y. For exam- ple: modify parts to heapsort on pnum:ascending, pname:descending 5519 MODIFY: %0 is a view and can't be modified Only physical relations can be modified. 5520 MODIFY: %0: sequence specifier "%1" on domain %2 is not allowed with the specified storage structure. Sortorder may be supplied only when modifying to _h_e_a_p_s_o_r_t or _c_h_e_a_p_s_o_r_t. 5600 SAVE: cannot save system relation "%0" System relations have no save date and are guaranteed to stay for the lifetime of the data base. 5601 SAVE: bad month "%0" 5602 SAVE: bad day "%0" 5603 SAVE: bad year "%0" This was a bad month, bad day, or maybe even a bad year for INGRES. 5604 SAVE: relation %0 does not exist or is not owned by you 5800 COPY: relation %0 doesn't exist 5801 COPY: attribute %0 in relation %1 doesn't exist or it has been listed twice 5803 COPY: too many attributes Each dummy domain and real domain listed in the copy statement count as one attribute. The limit is 150 attributes. 5804 COPY: bad length for attribute %0. Length="%1" 5805 COPY: can't open file %0 On a copy "from", the file is not readable by the user. 5806 COPY: can't create file %0 On a copy "into", the file is not creatable by the user. This is usually caused by the user not having write permission in the specified directory. 5807 COPY: unrecognizable dummy domain "%0" On a copy "into", a dummy domain name is used to in- sert certain characters into the unix file. The domain name given is not valid. 5808 COPY: domain %0 size too small for conversion. There were %2 tuples successfully copied from %3 into %4 When doing any copy except character to character, copy checks that the field is large enough to hold the value being copied. 5809 COPY: bad input string for domain %0. Input was "%1". There were %2 tuples successfully copied from %3 into %4 This occurs when converting character strings to in- tegers or floating point numbers. The character string contains something other than numeric charac- ters (0-9,+,-,blank,etc.). 5810 COPY: unexpected end of file while filling domain %0. There were %1 tuples successfully copied from %2 into %3 5811 COPY: bad type for attribute %0. Type="%1" The only accepted types are i, f, c, and d. 5812 COPY: The relation "%0" has a secondary index. The index(es) must be destroyed before doing a copy "from" Copy cannot update secondary indices. Therefore, a copy "from" cannot be done on an indexed relation. 5813 COPY: You are not allowed to update the relation %0 You cannot copy into a system relation or secondary index. 5814 COPY: You do not own the relation %0. You cannot use copy to update a relation which you do not own. A copy "into" is allowed but a copy "from" is not. 5815 COPY: An unterminated "c0" field occurred while fil- ling domain %0. There were %1 tuples successfully copied from %2 into %3 A string read on a copy "from" using the "c0" option cannot be longer than 1024 characters. 5816 COPY: The full pathname must be specified for the file %0 The file name for copy must start with a "/". 5817 COPY: The maximum width of the output file cannot exceed 1024 bytes per tuple The amount of data to be output to the file for each tuple exceeds 1024. This usually happens only if a format was mistyped or a lot of large dummy domains were specified. 5818 COPY: %0 is a view and can't be copied Only physical relations can be copied. 5819 COPY: Warning: %0 duplicate tuples were ignored. On a copy "from", duplicate tuples were present in the relation. 5820 COPY: Warning: %0 domains had control characters which were converted to blanks. 5821 COPY: Warning: %0 c0 character domains were truncat- ed. Character domains in c0 format are of the same length as the domain length. You had a domain value greater than this length, and it was truncated. 5822 COPY: Relation %0 is protected. You are not authorized to access this relation.